Open Source Unix Shell Version Control Software
Sort By:
Unix Shell Version Control Software
View 83 business solutionsBrowse free open source Unix Shell Version Control Software and projects below. Use the toggles on the left to filter open source Unix Shell Version Control Software by OS, license, language, programming language, and project status.
-
$300 Free Credits to Build on Google CloudPut your $300 in credit toward real workloads, then keep building with free monthly usage for 20+ products. No commitment and no charge until you upgrade.
-
Demo Series - Small Business Backup By VeeamWatch this on-demand demo series and learn how to protect your Microsoft 365 data with clear, simple, actionable steps that are easy to implement for businesses of all sizes.
-
1
-
2
asdf
Extendable version manager with support for Ruby, Node.js, Elixir, etc
Manage multiple runtime versions with a single CLI tool. Manage each of your project runtimes with a single CLI tool and command interface. asdf is a CLI tool that can manage multiple language runtime versions on a per-project basis. It is like gvm, nvm, rbenv & pyenv (and more) all in one! Simply install your language's plugin! Large ecosystem of existing runtimes & tools. Simple API to add support for new tools as you need! Support for existing config files .nvmrc, .node-versions, .ruby-version for smooth migration! .tool-versions to manage all your tools, runtimes, and their versions in a single, sharable place. Supports Bash, ZSH, Fish & Elvish with completions available. Provides a GitHub Action to install and utilize your .tool-versions in your CI/CD workflows. -
3
Git Blame Someone Else
Blame someone else for your bad code
git-blame-someone-else is a humorous Git utility created as a joke to let developers attribute problematic code to someone else. It modifies both the author and committer information of a commit, making it appear as though another contributor is responsible for the changes. While not intended for production repositories, it demonstrates how Git’s metadata can be manipulated for fun or demonstration purposes. The project highlights how easily commit authorship can be altered, serving as both a lighthearted tool and a reminder about the importance of trust in version control history. It’s written in shell script and is lightweight, requiring only Git and basic system tools to run. Despite being a novelty project, its popularity shows how developers appreciate humor injected into the programming ecosystem. -
4
git-recall
An interactive way to peruse your git history from the terminal
An interactive way to peruse your git history from the terminal. git-recall is a simple tool that allows you to easily go through your commits and check what you or other contributors in your team did. It doesn't aim to be a replacement for the git log command, but just to be a convenient way to recall what you've done from your terminal. You can install it by simply copying the git-recall script into any existing path (e.g. /usr/local/bin) or create your own directory and add it to the PATH variable. Once the commits are displayed, you can use either the arrow keys or j/k to switch between commits, press TAB or e to expand/reduce the commit's diff or q to quit. -
Endpoint Management with Remote Control Built InSplashtop AEM handles patching, alerts, scripts, and inventory, and unattended remote control is included. When something needs hands-on work, you’re one click away instead of switching tools.
-
5
Provide secure and stable OS, based on highly modified Linux Kernel, own package system, like "BSD Ports". Compatible with x86, Power PC. Easy to use of any level users. Complete Documentantion in many languages. 99% compatible with Windows.
-
6
forgit
A utility tool powered by fzf for using git interactively
This tool is designed to help you use git more efficiently. It's lightweight and easy to use. Fig adds apps, shortcuts, and autocomplete to your existing terminal. Options can be set via environment variables. They have to be exported in order to be recognized by forgit. You can use forgit as a subcommand of git by making git-forgit available in $PATH. Forgit will use the default configured pager from git (core.pager, pager.show, pager.diff) but can be altered with several environment variables. You can add default fzf options for forgit, including keybinds, layout, etc. (No need to repeat the options already defined. -
7
pyenv
Simple Python version management
pyenv is a tool for the simple management of Python versions: it lets you easily switch between different Python versions, offering support for per-project Python versions. pyenv is an uncomplicated, unobtrusive tool that simply works, and follows the UNIX tradition of single-purpose tools that do one thing well. Unlike other similar tools, pyenv does not depend on Python itself. Having been made from pure shell scripts, it's safe from a Python bootstrap problem. It doesn't need to be loaded into your shell thanks to its shim approach, and can manage virtualenv for you. pyenv is a fork of rbenv and ruby-build, modified for Python. -
8
git-flow (AVH Edition)
AVH Edition of the git extensions to provide high-level repository ops
A collection of Git extensions to provide high-level repository operations for Vincent Driessen's branching model. This fork adds functionality not added to the original branch. For those who use the Bash or ZSH shell, you can use my fork of git-flow-completion which includes several additions for git-flow (AVH Edition), or you can use the original git-flow-completion project by bobthecow. Both offer tab-completion for git-flow subcommands and branch names with my fork including tab-completion for the commands not found in the original git-flow. For a wide variety of commands hooks or filters can be called before and after the command. The files should be placed in .git/hooks In the directory hooks you can find examples of all the hooks available. You can easily publish a feature you are working on. The reason can be to allow other programmers to work on it or to access it from another machine. -
9
Husky
Git hooks made easy
Husky is a tool that makes handling Git hooks a lot easier, and lets you run the scripts you want at those stages. It works by including an object right within your package.json file. This then configures Husky so that it runs the scripts you specify. After that, it's Husky's responsibility to manage at which point in the Git lifecycle your scripts will run. Husky helps to improve your commits, lets you run tests, lint code and more when you commit or push. It is very lightweight, with zero dependencies and is capable of supporting all Git hooks. -
Go from Code to Production URL in SecondsSkip the Kubernetes configs. Cloud Run handles HTTPS, scaling, and infrastructure automatically. Two million requests free per month.
-
10
git-auto-commit Action
Automatically Commit changed Files back to GitHub
Automatically Commit changed Files back to GitHub with GitHub Actions for the 80% use case. A GitHub Action to detect changed files during a Workflow run and to commit and push them back to the GitHub repository. By default, the commit is made in the name of "GitHub Actions" and co-authored by the user that made the last commit. Note that the Action has to be used in a Job that runs on a UNIX system (e.g. ubuntu-latest). If you don't use the default permission of the GITHUB_TOKEN, give the Job or Workflow at least the contents: write permission. The goal of this Action is to be "the Action for committing files for the 80% use case". Therefore, you might run into issues if your Workflow falls into the not supported 20% portion. If your Workflow can't push the commit to the repository because of authentication issues, please update your Workflow configuration. -
11
transcrypt git
transparently encrypt files within a git repository
A script to configure transparent encryption of sensitive files stored in a Git repository. Files that you choose will be automatically encrypted when you commit them, and automatically decrypted when you check them out. The process will degrade gracefully, so even people without your encryption password can safely commit changes to the repository's non-encrypted files. transcrypt protects your data when it's pushed to remotes that you may not directly control (e.g., GitHub, Dropbox clones, etc.), while still allowing you to work normally on your local working copy. You can conveniently store things like passwords and private keys within your repository and not have to share them with your entire team or complicate your workflow. transcrypt is in the same vein as existing projects like git-crypt and git-encrypt, which follow Git's documentation regarding the use of clean/smudge filters for encryption. -
12
Shell Package Manager
Install packages that apt-get can't.
Sh scripts for (un)installing packages that can't be installed by default with apt-get. -
13
The SoftChange project will create software to summarize and analyze software changes in CVS repositories and defect tracking systems (Bugzilla/GNATS).
-
14
bfm
BigFileManager - Manage files outside of your VCS
This tool is intended to manage big files out of your VCS but in your workarea. It's like mercurial largefile extension but independend of any VCS. Instead of the big file itself only a list of filenames with their checksums (md5) are committed to the VCS. The BFM can check for missing or outdated bigfiles and downloads them from a server using CURL. -
15
A plug-in element for CruiseControl to detect tag related modifications in a source code repository (CVS).
-
16
The Ape Base Compile System is a set of bash scripts to leverage both ESP EPM (http://www.epmhome.org/) and MREPO (http://dag.wieers.com/home-made/mrepo/) in maintaining applications such as as Apache HTTPD, MySQL or PHP on Red Hat based systems.
-
17
The aim of this project is to make it easier to keep the source code updated with the server on projects that use CVS. Keeping up to date source files on SourceForge.com projects will be automated.
-
18
BTS is a Build Template System designed for building packages for th common packing systems in use by current distributions based on a single XML package description. We are finally restarting development after a long break due to NeOS work.
-
19
CODESH
Automatic persistent logbooks for Linux shell sessions (bash, tcsh...)
The CODESH (COllaborative DEvelopment SHell) project provides an automatic persistent logbook for sessions of personal command-line work by recording what and how is being done: for private use/reuse and for sharing selected parts with collaborators. -
20
CSSC is a clone of the Unix SCCS tool suite. CSSC is useful for working with existing source respositories that are already in SCCS format.
-
21
The enclosed Python scripts differ from most other commit notification solutions in that they coalesce all of the commit operations from a single \\\"cvs commit\\\" command into a single email. Most other solutions will send one email per directory.
-
22
This project provides a coherent package of utilities that simplify the task of tagging, customising and packaging releases of code taken from CVS, together with documentation about release conventions and suggested practices.
-
23
CVS tools - set of utilities for users, project/build managers and system administrators. The tools use platform independent languages like bash, Perl, Python or Java. Platform support Win32/Cygwin and Linux based file systems. PROJECT MOVED. See Github user jaalto.
-
24
-
25
Corredor is a robust general framework for performing software test automation. The suite aims to simplify the set up, maintenance, and running of tasks, supporting remote distribution, parallel execution, & dependancy hierarchies.
